<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="zh" xml:lang="zh" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<head>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Concept: Developing Service-Oriented Solutions</title>
<meta name="uma.type" content="Concept">
<meta name="uma.name" content="developing_service-oriented_solutions">
<meta name="uma.presentationName" content="Developing Service-Oriented Solutions">
<meta name="element_type" content="concept">
<meta name="filetype" content="description">
<meta name="role" content="">
<link rel="StyleSheet" href="./../../../css/default.css" type="text/css">
<script src="./../../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
					var backPath = './../../../';
					var imgPath = './../../../images/';
					var nodeInfo=null;
					contentPage.preload(imgPath, backPath, nodeInfo,  '', false, false, false);
				</script>
</head>
<body>
<div id="breadcrumbs"></div>
<table border="0" cellpadding="0" cellspacing="0" width="100%">
<tr>
<td valign="top"><a name="Top"></a>
<div id="page-guid" value="3.300952218919066E-305"></div>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td class="pageTitle" nowrap="true">Concept: Developing Service-Oriented Solutions</td><td width="100%">
<div align="right" id="contentPageToolbar"></div>
</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../../scripts/treebrowser.js"></script></td>
</tr>
</table>
<table width="100%" border="0" cellpadding="0" cellspacing="0">
<tr>
<td class="pageTitleSeparator"><img src="./../../../images/shim.gif" alt="" title="" height="1"></td>
</tr>
</table>
<div class="overview">
<table width="97%" border="0" cellspacing="0" cellpadding="0">
<tr>
<td width="50"><img src="./../../../rup_soa_plugin/guidances/concepts/resources/road_lg_dgm32.gif" alt="" title=""></td><td>
<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
<tr>
<td valign="top">This concept page describes a roadmap through the Neusoft Unified Process (RUP) when developing service-oriented solutions.</td>
</tr>
</table>
</td>
</tr>
</table>
</div>
<div class="sectionHeading">Main Description</div>
<div class="sectionContent">
<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
<tr valign="top">
<td class="sectionTableSingleCell"><h6 align="left">
    <b><font size="2">Activities across the lifecycle:</font></b>
</h6>
<div align="left">
    <ol>
        <li>
            <a href="#Introduction">Introduction</a>
        </li>
        <li>
            <a href="#Inception Phase Activities">Inception Phase Activities</a>
        </li>
        <li>
            <a href="#Elaboration Phase Activities">Elaboration Phase Activities</a>
        </li>
        <li>
            <a href="#Construction Phase Activities">Construction Phase Activities</a>
        </li>
        <li>
            <a href="#Transition Phase Activities">Transition Phase Activities</a>
        </li>
    </ol>
</div>
<table>
    <tbody>
        <tr>
            <td width="284" height="102">
                <h6 align="left">
                    <b><font size="2">Additional topics:</font></b>
                </h6>
                <div align="left">
                    <ul>
                        <li>
                            <b>Concepts</b><br />
                            <ul>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service-oriented_architecture_8328ABAD.html" guid="8.613638237693525E-307">Service-Oriented Architecture</a>
                                </li>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service_composition_and_choreography_41EDEECB.html" guid="7.723783423994501E-306">Service Composition and Choreography</a>
                                </li>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/solution_partitioning_352116F8.html" guid="1.6501323286225543E-305">Solution Partitioning</a>
                                </li>
                                <li>
                                    <a class="elementLink" href="./../../../rup_soa_plugin/guidances/concepts/domain_design_77B2F855.html" guid="1.2602759670310655E-305">Domain Design</a>
                                </li>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service_portfolio_52FD64AC.html" guid="1.851952881072508E-305">Service Portfolio</a>
                                </li>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/message_design_DA8438ED.html" guid="5.580979266831891E-307">Message Design</a>
                                </li>
                            </ul><br />
                        </li>
                        <li>
                            <b>Guidelines</b><br />
                            <ul>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/going_from_services_to_service_components_914EA328.html" guid="2.4211910729992714E-305">Going from Services to Service Components</a>
                                </li>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/message_attachments_AE665E63.html" guid="7.676056734461877E-306">Message Attachments</a>
                                </li>
                                <li>
                                    <a class="elementLink" href="./../../../rup_soa_plugin/guidances/guidelines/service_CA5D991C.html" guid="2.1757522381974088E-306">Service</a>
                                </li>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/service_data_encapsulation_F424F20E.html" guid="1.6727924656888407E-305">Service Data Encapsulation</a>
                                </li>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/service_mediation_2F2C4C02.html" guid="2.5614739075754752E-306">Service Mediation</a>
                                </li>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/state_management_for_services_E4156B50.html" guid="4.2228409903513537E-306">State Management for Services</a>
                                </li>
                            </ul><br />
                        </li>
                        <li>
                            <b>White Papers</b><br />
                            <ul>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/whitepapers/soa_cbd_paper_5703509E.html" guid="2.48704851646278E-307">Using Service-Oriented Architecture and Component-Based
                                    Development to Build Web Service Applications</a>
                                </li>
                                <li>
                                    <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/whitepapers/uml_profile_for_software_services_7ADFB3D2.html" guid="2.972928238097629E-306">UML 2.0 Profile for Software Services</a>
                                </li>
                            </ul><br />
                        </li>
                    </ul>
                </div>
            </td>
        </tr>
    </tbody>
</table>
<h3>
    <a id="Introduction" name="Introduction">Introduction</a>
</h3>The adaptation of the Neusoft Unified Process (RUP) for Services and Service-Oriented Architecture (SOA) is described
in the following sections. 
<h3>
    <a id="Inception Phase Activities" name="Inception Phase Activities">Inception Phase Activities</a>
</h3>
<p>
    The basic workflow for the <a class="elementLinkWithUserText" href="./../../../rup/customcategories/inception_D506BCB4.html" guid="_vyZOwCVuEdqSZ9OimJ-AzA">Inception Phase</a>
    applies, with the following extensions or variations:
</p>
<h4>
    <a id="Inception_Project" name="Inception_Project">Project Management</a>
</h4>
<ul>
    <li>
        <a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/conceive_new_project_E9B31C9F.html" guid="{76FD7B68-FC91-488D-BBF1-6FE58DBACB87}">Activity: 构思新项目</a> 
        <p class="node">
            The focus of the <a class="elementLinkWithType" href="./../../../rup/tasks/develop_business_case_F985B634.html" guid="{F7A5D34A-A8B1-466D-BE41-FFCD41B4430D}">Task: 开发商业理由</a> is adjusted to take into account that reusing
            existing internal and external services change the cost structure of development. Specifically, the cost of
            developing services decreases, but more effort is spent identifying services and validating that selected
            services meet their requirements. See the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service-oriented_architecture_8328ABAD.html" guid="8.613638237693525E-307">Concept: Service Oriented Architecture</a> and the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service_portfolio_52FD64AC.html" guid="1.851952881072508E-305">Concept: Service Portfolio</a> for more information.
        </p>
    </li>
</ul>
<ul>
    <li>
        <a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/evaluate_project_scope_and_risk_C777352.html" guid="{BADBA2C5-144D-482B-9B63-C95DA4DBD3E5}">Activity: 评估项目范围和风险</a> 
        <p class="node">
            Developing a service-oriented solution changes the nature of certain risks and introduces new risks.
            Specifically:
        </p>
        <ul>
            <li>
                Externally sourced services increase risk because they introduce critical elements not under the project
                team's direct control.
            </li>
            <li>
                Externally sourced services can reduce development time, reducing resource risk
            </li>
            <li>
                Externally sourced services may introduce security and quality-of-service policies that are not inline with
                internal architectural guidelines
            </li>
        </ul>
    </li>
</ul>
<ul>
    <li>
        <a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/plan_the_project_DD2EE35.html" guid="{823EF41B-2BD1-464B-84DB-C7BD432636E2}">Activity: 规划项目</a> 
        <p class="node">
            In the <a class="elementLinkWithType" href="./../../../rup/tasks/plan_phases_and_iterations_2AB1A5C9.html" guid="{43005DA9-D75E-464D-8AFC-AB9CACD92626}">Task: 计划阶段和迭代</a>, the plan for the Construction phase may show
            the project splitting into three different but parallel tracks: one which develops the application-specific
            services, one which develops reusable domain-specific services, and the reusable infrastructure services. The
            decision to introduce parallel tracks is largely a staffing and resource issue introduced by a desire to manage
            services as reusable assets independent of the applications in which they are deployed. See the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service_portfolio_52FD64AC.html" guid="1.851952881072508E-305">Concept: Service Portfolio</a> for more information on the categorization of
            services.
        </p>
    </li>
</ul>
<h4>
    <a id="Inception_Business" name="Inception_Business">Business Modeling</a>
</h4>
<ul>
    <li>
        <b>Activity: <a class="elementLinkWithUserText" href="./../../../rup_bm/capabilitypatterns/Identify Business Processes_8B735C24.html" guid="_JnU6kTXEEdq4lJjndbo9Yw">Identify Business Processes</a> and&nbsp;<a class="elementLinkWithUserText" href="./../../../rup_bm/capabilitypatterns/explore_process_automation_64AC8E95.html" guid="_ITAWgDXFEdq4lJjndbo9Yw">Explore Process Automation</a></b> 
        <p class="node">
            In the <a class="elementLinkWithType" href="./../../../rup_bm/tasks/bm_architectural_analysis_630ADB6.html" guid="_xfhhcBpWEdqUwb9RAn2tTA">Task: 业务架构分析</a>&nbsp;and the <a class="elementLinkWithType" href="./../../../rup_bm/tasks/identify_business_goals_BDD1599E.html" guid="{BE3CF670-F2E7-4B03-90A0-F01B59777597}">Task: 确定业务目标</a> the key forces that affect the business and the
            business strategy are outlined. It is important that these tasks be aligned to services being developed to
            support the business.So, in the task <i><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/tasks/identify_services_565F8B8A.html" guid="{0BF79161-A484-4C48-B72D-DA381DA05886}">Identify Services</a></i>, the traceability from <i><a class="elementLinkWithUserText" href="./../../../rup_bm/workproducts/rup_business_goal_D99D08F9.html" guid="{6DC6732B-E7F1-495E-B5EC-AEBFD7BE80FE}">Business Goals</a></i> through to <i><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_svce_model_service_1EE4C96C.html" guid="{FF65B0A2-6C53-4F01-9727-AACDB0D542C8}">Services</a></i> is explored in more detail. It is also important
            that, as service-oriented solutions are more aligned with the business and therefore the business architecture,
            the key elements of the IT services become reflected through to the business.
        </p>
    </li>
</ul>
<h4>
    <a id="Inception_Requirements" name="Inception_Requirements">Requirements</a>
</h4>
<ul>
    <li>
        <a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/manage_the_scope_of_the_system_7E0B34E5.html" guid="{CA9197A9-051E-4845-A7FC-2A8750BD8C02}">Activity: 管理系统范围</a> 
        <p class="node">
            In the <a class="elementLinkWithType" href="./../../../rup/tasks/manage_dependencies_4F6CEFAA.html" guid="{7F42C4D6-584F-4B19-9B0B-FDE86BD85FBB}">Task: Manage Dependencies</a>, the solution's requirements should
            be managed with the autonomy of services in mind. Services with fewer dependencies are more autonomous and
            therefore more reusable. See also the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/reports/service_dependencies_D8D49422.html" guid="1.2262765587812462E-305">Report: Service Dependencies</a>.
        </p>
    </li>
</ul>
<h4>
    <a id="Inception_Design" name="Inception_Design">Analysis & Design</a>
</h4>
<ul>
    <li>
        <b><a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/perform_architectural_synthesis_B63930B9.html" guid="{C67C8E56-D9B6-499C-8171-C153FB28F1C3}">Activity: 执行架构合成</a></b> 
        <p class="node">
            In the <a class="elementLinkWithType" href="./../../../rup/tasks/architectural_analysis_2B9BE03.html" guid="{8CB48402-D4C5-4E17-BB33-507315CB1BBF}">Task: 架构分析</a>, a number of the identified steps are affected
            by the development of service-oriented solutions. The survey of available assets can reuse the <i><a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service_portfolio_52FD64AC.html" guid="1.851952881072508E-305">Service Portfolio</a></i> models to gather information on existing services and
            their capabilities. Also, the development of the deployment overview has to take into account the middleware
            platforms to be used for service implementation and deployment.
        </p>
    </li>
</ul>
<h4>
    <a id="Inception_Test" name="Inception_Test">Test</a>
</h4>
<ul>
    <li>
        <a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/define_evaluation_mission_611C79D9.html" guid="{10C2C34C-BF5E-4825-A7DC-5E106EFAA4C5}">Activity: 定义评估任务</a> 
        <p class="node">
            In the <a class="elementLinkWithType" href="./../../../rup/tasks/identify_test_targets_693323A6.html" guid="{FFBDC174-FA91-4712-ABE2-7580A5670E8D}">Task: Identify Targets of Test</a>, the test strategy should take
            into account the autonomous nature of services and ensure adequate stand-alone tests for each service and tests
            for the collaboration of services when they interact with each other.
        </p>
    </li>
</ul>
<h4>
    <a id="Inception_Environment" name="Inception_Environment">Environment</a>
</h4>
<ul>
    <li>
        <a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/prepare_environment_for_project_5F602A4.html" guid="{37A50EF5-CC73-4E38-B851-997879548110}">Activity: 准备项目环境</a> 
        <p class="node">
            When collecting and preparing guidelines for the project, see <a class="elementLinkWithType" href="./../../../rup/tasks/prepare_project_specific_guidelines_A9AD00DB.html" guid="{1E706674-C1E7-4F8D-BF06-35FFE49C5E42}">Task: Prepare Guidelines for the Project</a> for details, take
            into account the specific set of technologies and standards to be used in developing services. Guidelines
            should include how the particular set of standards for service definition, policy identification and security.
            They should also provide testing guidance on how to verify conformance with <b>both</b> the standards
            themselves (see <a href="http://www.ws-i.org/">WS-I</a> for information on Web Service standards conformance)
            and the interfaces defined between components.
        </p>
    </li>
</ul>
<h3>
    <a id="Elaboration Phase Activities" name="Elaboration Phase Activities">Elaboration Phase Activities</a>
</h3>
<p>
    The basic workflow for the <a class="elementLinkWithUserText" href="./../../../rup/customcategories/elaboration_6A203A50.html" guid="_-kFhcCVuEdqSZ9OimJ-AzA">Elaboration Phase</a>
    applies, with the following extensions or variations:
</p>
<h4>
    <a id="Elaboration_Requirements" name="Elaboration_Requirements">Requirements</a>
</h4>
<ul>
    <li>
        <a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/refine_the_system_definition_E67B8011.html" guid="{0FEE5795-6090-4D82-9BDB-925E5F0D9985}">Activity: 优化系统定义</a> 
        <p class="node">
            The <a class="elementLinkWithType" href="./../../../rup/tasks/detail_software_requirements_A7F0A215.html" guid="{A1FA1E95-8028-42EB-9B92-0DA77380F3E1}">Task: 详细描述软件需求</a> additionally focuses on the technical and
            non-functional requirements and constraints imposed on the services that are either built or purchased.
            Specific non-functional requirements to consider are performance, security, infrastructure requirements,
            service dependencies, run-time licensing issues, and similar constraints that will influence service selection
            or construction.
        </p>
    </li>
</ul>
<h4>
    <a id="Elaboration_Design" name="Elaboration_Design">Analysis & Design</a>
</h4>
<ul>
    <li>
        <a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/define_a_candidate_architecture_A3651DA3.html" guid="{71ADFE9A-34A0-41BD-8A17-BEA3210E2BBD}">Activity: 定义候选架构</a> 
        <p class="node">
            The <a class="elementLinkWithType" href="./../../../rup/tasks/architectural_analysis_2B9BE03.html" guid="{8CB48402-D4C5-4E17-BB33-507315CB1BBF}">Task: 架构分析</a> assumes a <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service-oriented_architecture_8328ABAD.html" guid="8.613638237693525E-307">service-oriented architectural style</a> and uses the technical and
            non-functional requirements to define the detailed architecture, including initial partitioning of the solution
            and a default set of and services represented using the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/workproducts/soa_service_model_623494B9.html" guid="{E24679B7-19F1-483B-A1F1-578839C43888}">Work Product: Service Model</a>.
        </p>
    </li>
    <li>
        <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/capabilitypatterns/design_services_45CC7C36.html" guid="_6Jd70DtdEdqPaeZADstHAA">Design Services</a> 
        <p class="node">
            In the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/tasks/identify_services_565F8B8A.html" guid="{0BF79161-A484-4C48-B72D-DA381DA05886}">Task: Identify Services</a>, the services are identified, using a
            number of techniques to develop an initial service model. In the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/tasks/soa_service_design_AB6BA763.html" guid="{9EB2B302-79F6-4DF8-AEB7-98E6AC1756DD}">Task: Service Design</a> these candidate services are modeled in
            detail and their operations are specified with message input/output requirements. See the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/message_design_DA8438ED.html" guid="5.580979266831891E-307">Concept: Message Design</a> for more information.
        </p>
    </li>
</ul>
<ul>
    <li>
        <a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/design_components_13B33BFC.html" guid="{9C683674-97C1-4AEE-8DB0-9514AEFF698E}">Activity: 设计组件</a> 
        <p class="node">
            The <a class="elementLinkWithType" href="./../../../rup/tasks/subsystem_design_5D1BCC0C.html" guid="{CAA385CA-2BA2-40F2-8FE3-E21089D02119}">Task: 子系统设计</a> further refines the
            design of the service, identifying subsystems within the service which provide the real behavior of the
            service. In the early stages of the elaboration phase, there is likely to be a single component which acts as a
            stub to simulate the behavior of the service for architectural prototyping purposes. Later, the behavior of
            this component is distributed to a collaboration of classes contained within the subsystem. See the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/concepts/service-oriented_architecture_8328ABAD.html" guid="8.613638237693525E-307">Concept: Service-Oriented Architecture</a> for more detail on the relationship
            between services, components and classes.
        </p>
    </li>
</ul>
<ul>
    <li>
        <a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/design_the_database_2BE59DB0.html" guid="{FB3EB753-A979-4849-B57B-97F39271F82B}">Activity: 设计数据库</a> 
        <p class="node">
            The focus in elaboration is on ensuring that the service encapsulates its data requirements completely and that
            dependencies between services do not arise due to the introduction of services that should be using the same
            data source. For more information, see the <a class="elementLinkWithUserText" href="./../../../rup_soa_plugin/guidances/guidelines/service_data_encapsulation_F424F20E.html" guid="1.6727924656888407E-305">Guideline: Service Data Encapsulation</a>.
        </p>
    </li>
</ul>
<h4>
    <a id="Elaboration_Test" name="Elaboration_Test">Test</a>
</h4>
<ul>
    <li>
        <b>Activity Detail: <a class="elementLink" href="./../../../rup/capabilitypatterns/define_evaluation_mission_611C79D9.html" guid="{10C2C34C-BF5E-4825-A7DC-5E106EFAA4C5}">定义评估任务</a>, <a class="elementLink" href="./../../../rup/capabilitypatterns/verify_test_approach_A743008A.html" guid="{7BD514AF-19F9-408F-8279-309BD153C157}">验证测试方法</a>, <a class="elementLink" href="./../../../rup/capabilitypatterns/test_and_evaluate_4D17BD6A.html" guid="{93B7D625-C83A-4EFB-9772-B88F2EB02CE2}">测试和评估</a>, <a class="elementLink" href="./../../../rup/capabilitypatterns/achieve_acceptable_mission_18DE9944.html" guid="{5DA9C9E9-1538-4433-8B57-B28667D67514}">实现可接受的任务</a>, <a class="elementLink" href="./../../../rup/capabilitypatterns/improve_test_assets_1C99FFB9.html" guid="{CD77CBDA-CC13-4593-BB81-41AF3FF7A84C}">改善测试资产</a></b> 
        <p class="node">
            The testing tasks in elaboration focus on validating the individual services. For a service-oriented solution,
            this focus translates to:
        </p>
        <ul>
            <li>
                Exercising the interfaces between services, to ensure that service boundaries are appropriate.
            </li>
            <li>
                A focus on the complete service specification, to ensure that service implementations fulfill their
                obligations.
            </li>
            <li>
                A greater focus on performance testing, especially performance scaling tests, to ensure that anticipated
                transaction volumes can be sustained.
            </li>
        </ul>
    </li>
</ul>
<h3>
    <a id="Construction Phase Activities" name="Construction Phase Activities">Construction Phase Activities</a>
</h3>
<p>
    The basic workflow for the <a class="elementLinkWithUserText" href="./../../../rup/customcategories/construction_102AF1EA.html" guid="_SkuIwCVwEdqSZ9OimJ-AzA">Construction Phase</a>
    applies, with the following extensions or variations:
</p>
<h4>
    <a id="Construction_Design" name="Construction_Design">Analysis & Design</a>
</h4>
<ul>
    <li>
        <b>Activity Details: <a class="elementLink" href="./../../../rup/capabilitypatterns/refine_the_architecture_F40FA195.html" guid="{F2160C54-F666-4736-9982-FC7F58F15FAD}">优化架构</a> and <a class="elementLink" href="./../../../rup/capabilitypatterns/design_components_13B33BFC.html" guid="{9C683674-97C1-4AEE-8DB0-9514AEFF698E}">设计组件</a></b> 
        <p class="node">
            The focus in construction is on analyzing the remainder of the business-use cases, system-use cases, or
            business-process models and identifying appropriate services and service collaborations that realize these. The
            existing architecture is expanded and completed and the 'internal behaviors' of the component are completely
            designed, implemented and tested against their specifications. Specifically the <a class="elementLinkWithType" href="./../../../rup/tasks/identify_design_elements_E884AB82.html" guid="{97D7343A-6993-4AB7-8F86-4DAC8C9075C8}">Task: 确定设计元素</a>, <a class="elementLinkWithType" href="./../../../rup/tasks/identify_design_mechanisms_9A197FBC.html" guid="{C7A26BD7-3820-48D9-830F-684C3AF155F9}">Task: 确定设计机制</a> and <a class="elementLinkWithType" href="./../../../rup/tasks/incorporate_design_elements_D3C582B5.html" guid="{5C647173-4E32-4594-96A9-2548B47722FA}">Task: 合并现有设计元素</a> are extended to look specifically for services
            and related elements/mechanisms appropriate to the overall SOA.
        </p>
    </li>
</ul>
<h4>
    <a id="Construction_Implementation" name="Construction_Implementation">Implementation</a>
</h4>
<ul>
    <li>
        <b><a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/implement_components_AFD1799D.html" guid="{4DC6F53E-1FE1-44EE-812B-003D3BD1ACEA}">Activity: 实现组件</a></b> 
        <p class="node">
            It is important to realize that the move toward development of service-oriented solutions does not invalidate
            lessons learned from developing component-based solutions. In fact, components are used as the implementation
            artifacts for services. This can be done in two ways, as described below. In either case the approach taken to
            the development of components will depend on the runtime platform chosen.
        </p>
        <ul>
            <li>
                From the service model, generate Web service artifacts such as Web Services Description Language (WSDL 1.1)
                which act as a description of a service interface and generate the information about the location and
                protocols used to access an instance of a service. From these artifacts, most design tools can generate
                server stubs and client accessors for the specified service.
            </li>
            <li>
                From the service model, transform into either a system <a class="elementLinkWithUserText" href="./../../../rup/workproducts/rup_usecase_model_EF15E534.html" guid="{9C66F2EC-EDEB-4369-9AFB-04B9E7CBCB8E}">Use Case Model</a>, or a <a class="elementLink" href="./../../../rup/workproducts/rup_design_model_2830034D.html" guid="{8CDAEAD4-5E84-4F50-87FD-3240ED047DE7}">设计模型</a> that can be further refined to describe the
                implementation before generating an <a class="elementLink" href="./../../../rup/workproducts/rup_implementation_model_5858DB65.html" guid="{157E9B67-C619-410D-A927-F2CD217BF8FE}">实现模型</a> or programming language artifacts that represent the
                service implementation.
            </li>
        </ul>
    </li>
</ul>
<h3>
    <a id="Transition Phase Activities" name="Transition Phase Activities">Transition Phase Activities</a>
</h3>
<p>
    The basic workflow for the&nbsp;<a class="elementLinkWithUserText" href="./../../../rup/customcategories/transition_1018F224.html" guid="_cn2akCVwEdqSZ9OimJ-AzA">Transition Phase</a>
    applies, with the following extensions or variations:
</p>
<h4>
    <a id="Transition_Deployment" name="Transition_Deployment">Deployment</a>
</h4>
<ul>
    <li>
        <b><a class="elementLinkWithType" href="./../../../rup/capabilitypatterns/plan_deployment_C83CF0FB.html" guid="{9B5E6B08-625F-40DF-AA4E-0BD056C0553A}">Activity: 计划部署</a></b> 
        <p class="node">
            When developing service-oriented solutions it is important to remember that, for the most part, services are
            single-instance components of the solution. All applications reusing a service are using the same instance of a
            service. By comparison, in a component-based application, components are generally copied into an application
            and new instances created for each application. This leads to the following concerns:
        </p>
        <ul>
            <li>
                Generally, services do not have to be packaged for distribution; they are deployed in a single location,
                except where distribution or replication concerns require more than one instance.
            </li>
            <li>
                Changes to interfaces have <i>immediate</i> effect on <i>all</i> consumers. We cannot plan to roll out new
                versions of a service in a phased manner as we can with components.
            </li>
            <li>
                Requirements for infrastructure services such as security or management have to be in place before business
                or application services.
            </li>
            <li>
                Services will generally require additional metadata for deployment as dictated by the chosen runtime
                platform.
            </li>
        </ul>
    </li>
</ul><br /></td>
</tr>
</table>
</div>
<table class="copyright" border="0" cellspacing="0" cellpadding="0">
<tr>
<td class="copyright">Copyright &copy; 2008 版权所有 东软集团股份有限公司&nbsp; 联系邮箱:<a href="mailto:tcoe@neusoft.com">tcoe@neusoft.com</a></td>
</tr>
</table>
</td>
</tr>
</table>
</body>
<script type="text/javascript" language="JavaScript">
				contentPage.onload();
			</script>
</html>
